fix(api): npm installs no longer hang on better-auth's open peers (0.1.1) - #8

fix(api): npm installs no longer hang on better-auth's open peers (0.1.1)

…ard (PR #205 review)

- A (#5, #3, #6, #7): the definitions and collections anchors read the
  fragment's stored text when planned (checked against the planned Site,
  else ConflictError) and compare that text at batch time, so a site row
  stored verbatim anchors like any other. The canonical-rows job and its
  local-open run are removed: nothing depends on canonical site rows.
- B (#2, #4): in a site with reference fields every entry write carries the
  definitions anchor (status-only publishes included); the shared subquery
  only matches reference and repeater definitions, so a retyped key fails
  the batch.
- C (#0): usable members are one json_each count over the needed collection
  lists (six parameters, per-pair semantics kept).
- D (#8, #15): the list-values fingerprint format moves to 2, so rows built
  under the old readsOriginal rebuild once.
- E (#16): a referrer write naming an entry outside the field's collections
  is unknown_entry (422); reference_target_moved stays the move's 409.
- F (#12): a reference sub-field added over a key stored items hold is
  field_key_in_use, counted and guarded on the site CAS.
- G (#1): racing cases for the R3 narrowing in both orders, R13 for a move
  and a group change, the #2 interleaving, a verbatim site row, 22 blocking
  pairs, and SQL tests of the shared subquery.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>

…es, shownBy, picker folding)

- #0: the MCP precheck builds its asset skip set from full issue paths, as
  the store does, so an item-level issue no longer hides another item's
  non-image (precheck test).
- #1: fieldAssetRefs keeps every use's path (`paths`); fieldAssetIssues
  reports each use not under a skip path, the asset_refs rows still one per
  asset and field.
- #2, #3: editionReferences applies the edition field's write rules (where,
  a single target, maxItems, the 100-reference cap, repeater maxItems),
  reads values through a running rename's fromKey (storedKey) and writes
  them back under that key; every drop carries its reason.
- #7: shownBy leaves out only the row's own holder, so it no longer depends
  on pagination (suite case paging at 20 and 1).
- #8: the picker folds q and the candidates' titles and slugs with foldName
  in JS (case, diacritics, Turkish İ/ı) over at most 5,000 candidates read
  as small columns; tests with ASCII and non-ASCII uppercase.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com>